Recovery accountability system

ABSTRACT

A method and system for recovery accountability comprises adding at least one required action for display on a user device, with a partner device, displaying at least one required action on a user device, validating a user check-in and a user check-out associated with the at least one required action with the user device, tracking user completion of the at least one required action with the user device, and monitoring the user completion of the at least one required action with the partner device.

CROSS REFERENCE TO RELATED PATENT APPLICATIONS

This patent application claims the priority and benefit, under 35 U.S.C.§ 119(e), of U.S. Provisional Patent Application Ser. No. 62/936,348,filed Nov. 15, 2019, entitled “RECOVERY ACCOUNTABILITY SYSTEM.” U.S.Provisional Patent Application Ser. No. 62/936,348 is hereinincorporated by reference in its entirety.

TECHNICAL FIELD

Embodiments are generally related to the field of compliance andaccountability. Embodiments are also related to the field of compliancetools. Embodiments are further related to the field of computer devicesand mobile devices used for accountability and compliance. Embodimentsare also related to methods, systems, and devices for implementingaccountability and compliance indicators.

BACKGROUND

Human beings learn and grow throughout their lives. As we adapt to ourenvironment—for better or worse, we naturally learn to survive in ourenvironment. When people are adapted to an unhealthy environment, thebehavior patterns that allow them to thrive may not work anywhere else.Those patterns can keep people stuck in a hopeless loop of relapse andrecidivism, despite repeated efforts at rehabilitation. Without tools tochange, it doesn't matter how much a person knows they “ought to”change. In particular, people with substance abuse issues almostuniversally understand that their lifestyle is unsustainable, andpotentially life threatening, but they lack the tools to help themescape the cycle of self-destructive behavior.

Products or programs currently in use, drive forced compliance, andenforced accountability through passive monitoring. These systems areessentially based on negative reinforcement/“violation” centered models.In some cases, these systems include tools that are primitive andoutdated.

While it should be obvious that such tools, like sign in sheets and soforth, are easily falsifiable, the reality is that for many strugglingwith addiction, the relationship with monitoring tools, including toolsthat make use of technology present an ongoing game of “cat and mouse.”Forced accountability almost always leads to work arounds. For example,an addict may find someone to blow into their breathalyzer; manipulateankle bracelet monitoring, and seek windows in which they can shakefree. One common problem with current cell phone based systems is thatusers can hand their monitored phone to a friend or loved one so that itappears they are where they are supposed to be.

These systems are coercive, operating primarily through negativeoutcomes, threats and punishments. The systems do not encourage patientsto learn new skills, and do not reward small successes along the way. Assuch, these prior art approaches overwhelmingly fail. The numbers arestunning. Current approaches result in 80-90% recidivism in mostcircumstances.

Accordingly, there is a need in the art for methods and systems thataddress the accountability requirements necessary for recovery, thatinclude tools that help encourage accountability with positivereinforcement.

SUMMARY

The following summary is provided to facilitate an understanding of someof the innovative features unique to the embodiments disclosed and isnot intended to be a full description. A full appreciation of thevarious aspects of the embodiments can be gained by taking the entirespecification, claims, drawings, and abstract as a whole.

It is, therefore, one aspect of the disclosed embodiments to provideimproved methods and systems for compliance and accountability.

It is another aspect of the disclosed embodiments to provide a method,system, and apparatus for tracking and promoting accountability.

It is another aspect of the disclosed embodiments to provide methods,systems, and apparatuses for fostering improved recovery andaccountability.

In the embodiments herein, a system, method, and apparatus for fosteringrecovery and accountability is disclosed. The embodiments have two basicpurposes. The first, is to provide an interactive, real timerelationship between a user and their accountability partner or manager,through the disclosed systems, to provide the user the tools necessaryto learn to be accountable to themselves. In certain embodiments, themethods and systems can be used by those coming out of correctionsfacilities and entering drug or alcohol rehabilitation programs to meettheir legal requirements and/or aftercare responsibilities. However, inother embodiments, use cases can include other situations or socialstructures where a client/employee/patient is responsible for being in avariety of locations at different times, and where there is anaccountability partner who wants or needs to verify attendance at theseappointments.

In certain embodiments, the systems and methods include a module forcollecting location and image data, described herein as a “selfie signin” both to confirm the identity of an attendee and to limitfalsification, and to provide ongoing, real time confirmations ofattendance across multiple, often disparate areas—i.e., medical,judicial, and drug testing appointments; work; school; communityservice; in the case of student athletes, attendance at a variety ofclasses, at tutoring, practice, workouts etc.

The second aspect is to provide a system for collecting analyticinformation on various levels, such analytic information beingindicative of the performance of each participant at their respectivelevel. The core of the disclosed embodiments is a database that allowsvarious categories of appointment (as further detailed herein) along oneaxis, and compliance metrics along the other axis. The layout ismodular, allowing for different categories in differentindustries/iterations.

Data collected through a mobile phone application or other such systemis aggregated at different hierarchies, i.e. for managers,administrators and organizations. Managers have access to real timeinformation about the clients' compliance, and may have risk indicatorsto flag those who are not signing in at their various appointments.Managers can see, in real time, whether clients are in full complianceand if not, what kinds of appointments they are missing. This allowsmanagers to target interventions and to make those interventions beforeproblems escalate.

In certain embodiments, the managers can fill a calendar that appears onthe clients' device. The appointments, including non-time-specificstipulations, populate the calendar and are available to the client onthe calendar and by push notification. The Client can add additionalappointments to the calendar but cannot remove appointments set by theiraccountability partner. Appointments can be moved, changed or cancelledin real time by the manager, allowing flexibility and accuracy inscheduling.

Data from clients (again, entered by clients as they go, therebyrequiring no further monitoring action from managers beyond setting thecalendar) is aggregated on several levels: the manager can see hisclients individually, and as a group; the administrator sees data fromclients and from individual managers' clients; a “superadmin” sees datafrom the various administrators who work under him, and so on. The“superuser” can have global access to the data. In certain embodiments,the data available to the superadmin can be deidentified data from allthe clients using the system and is able to aggregate across agencies,municipalities, and contexts.

The disclosed systems and methods can be realized as an accessibleresource platform that allows organizations to aggregate and sharecommunity support resources that might support a person as theytransition into a new way of life. This an include support resourcessuch as job agencies, food banks, housing support, fitness and yogaclasses, and scholarships and volunteer opportunities. The resourcelists can be provided via the methods and systems so that even when aclient leaves the locality at which they are admitted to a program, theycan continue to find the services they need and check-in, using thesystem, to establish compliance. Similar mobility support simply is notpossible using previous pen and paper check-in methods.

The resource platform also allows the client to find services they mayneed to complete the program without admitting to his accountabilitypartners the degree of his or her need. For example, often a clientneeding literacy services, food, or other basics will hesitate to sayso. Additionally, clients may be required to stay within proximity oftheir treatment/corrections program, even if they came from far away,because resources are unfamiliar and it's hard to keep track of theirprogress from further away. The resource platform allows clients todiscreetly find services they may need, allows treatment professionalsto refer to services including those outside their immediate area—and,ultimately, will allow different agencies and organizations to shareresource lists, allowing new levels of cooperation and collaboration.

The core of the disclosed systems gives people the tools to beginadapting to new parameters in their life. It starts with helping themtrack the myriad responsibilities they now have—and builds on successwith heavy doses of positive reinforcement for doing well, meetingmetrics, exceeding requirements, and continuing to move forward. Thesystem gives the user agency in relation to their own compliancemetrics, to help them learn to meet their goals for themselves. Byputting verification in the system instead of in the accountabilitypartner, the dynamic of that relationship can shift from one ofsuspicion to support.

An individual that learns and grows and improves and brings positivityto their family and friends. It webs out from the individual to thelarger community. Success in treatment both fosters and is contingent onhope, optimism, and positive reinforcement.

In an exemplary embodiment, an accountability system comprises a userdevice, the user device comprising a GPS receiver, a camera, and acomputer system, the computer system further comprising: at least oneprocessor, a graphical user interface, and a computer-usable mediumembodying computer program code, the computer-usable medium capable ofcommunicating with the at least one processor, the computer program codecomprising instructions executable by the at least one processor andconfigured for: displaying at least one required action, validating auser check-in and a user check-out associated with the at least onerequired action, and tracking user completion of the at least onerequired action.

The exemplary accountability system further comprises a partner device,the partner device comprising a second computer system, said secondcomputer system further comprising at least one processor and acomputer-usable medium embodying computer program code, thecomputer-usable medium capable of communicating with the at least oneprocessor, the computer program code comprising instructions executableby the at least one processor and configured for: adding the at leastone required action for display on the user device and monitoring theuser completion of the at least one required action. The accountabilitysystem further comprises an accountability module, the accountabilitymodule being configured for generating a calendar served to the clientdevice with a calendar module according to the at least one requiredaction added with the partner device.

In an embodiment the calendar module further displays the at least onerequired action on a calendar displayed on the user device.

In an embodiment, the accountability system further comprises a usersign in module, the user sign in module configured for: identifying acurrent time, identifying a current location of the user device, andcollecting an image of the user with the user device. In certainembodiment the system is configured for verifying the image of the useragainst a stored image, verifying the current location of the userdevice is within a geofenced location associated with a current requiredaction, and verifying the current time matches a time associated with acurrent required action.

In an embodiment, the system is configured for providing a resource listprovided on the user device with the graphical user interface.

In certain embodiments, the systems and methods include an alertsmodule, the alerts module configured for providing a notification of atleast one of: an upcoming required action and a missed required action.

In certain embodiment, the at least one required action furthercomprises a type comprising one of: a 12 step program, ajudicial/probation requirement, a testing requirement, an individualcounseling requirement, a group counseling requirement, a communityservice requirement, a medical requirement, a work requirement, and another requirement. The at least one required action displayed on theuser device can be color coded according to the type.

BRIEF DESCRIPTION OF THE FIGURES

The accompanying figures, in which like reference numerals refer toidentical or functionally-similar elements throughout the separate viewsand which are incorporated in and form a part of the specification,further illustrate the embodiments and, together with the detaileddescription, serve to explain the embodiments disclosed herein.

FIG. 1 depicts a block diagram of a computer system which is implementedin accordance with the disclosed embodiments;

FIG. 2 depicts a graphical representation of a network ofdata-processing devices in which aspects of the present embodiments maybe implemented;

FIG. 3 depicts a computer software system for directing the operation ofthe data-processing system depicted in FIG. 1, in accordance with anexample embodiment;

FIG. 4 depicts a block diagram of a system for accountability, inaccordance with the disclosed embodiments;

FIG. 5 depicts a block diagram of an accountability module, inaccordance with the disclosed embodiments;

FIG. 6 depicts a block diagram of a user portal, in accordance withdisclosed embodiments;

FIG. 7A depicts a home screen of a user interface of a user portaldisplayed on a user device, in accordance with the disclosedembodiments;

FIG. 7B depicts an upcoming appointments screen of a user interface of auser portal displayed on a user device, in accordance with the disclosedembodiments;

FIG. 7C depicts a weekly progress report screen of a user interface of auser portal displayed on a user device, in accordance with the disclosedembodiments;

FIG. 7D depicts a past appointments screen of a user interface of a userportal displayed on a user device, in accordance with the disclosedembodiments;

FIG. 7E depicts a weekly bonus appointments screen of a user interfaceof a user portal displayed on a user device, in accordance with thedisclosed embodiments;

FIG. 7F depicts a user interface of a sign-in module displayed on a userdevice, in accordance with the disclosed embodiments;

FIG. 7G depicts a user interface of a calendar module displayed on auser device, in accordance with the disclosed embodiments;

FIG. 7H depicts a user interface for adding appointment associated witha user portal displayed on a user device, in accordance with thedisclosed embodiments;

FIG. 8 depicts a block diagram of a partner portal, in accordance withdisclosed embodiments;

FIG. 9A depicts a user list of a user interface associated with apartner portal displayed on a partner device, in accordance with thedisclosed embodiments;

FIG. 9B depicts a user details on a user interface associated with apartner portal displayed on a partner device, in accordance with thedisclosed embodiments;

FIG. 9C depicts a weekly progress report displayed on a user interfaceassociated with a partner portal displayed on a partner device, inaccordance with the disclosed embodiments;

FIG. 9D depicts a weekly bonus appointments screen on a user interfaceassociated with a partner portal displayed on a partner device, inaccordance with the disclosed embodiments;

FIG. 9E depicts a compliance report displayed on a user interfaceassociated with a partner portal displayed on a partner device, inaccordance with the disclosed embodiments;

FIG. 9F depicts a calendar view displayed on a user interface associatedwith a partner portal displayed on a partner device in accordance withthe disclosed embodiments;

FIG. 9G depicts an interface for adding requirements associated with apartner portal displayed on a partner device, in accordance with thedisclosed embodiments;

FIG. 9H depicts a compliance report for a selected user displayed on auser interface associated with a partner portal displayed on a partnerdevice, in accordance with the disclosed embodiments;

FIG. 9I depicts a user status report displayed on a user interfaceassociated with a partner portal displayed on a partner device inaccordance with the disclosed embodiments;

FIG. 10 depicts a total report displayed on a user interface associatedwith a partner portal displayed on a partner device in accordance withthe disclosed embodiments;

FIG. 11 depicts hierarchical architecture of user layers, in accordancewith the disclosed embodiments;

FIG. 12 depicts steps in an accountability and recovery method, inaccordance with the disclosed embodiments; and

FIG. 13 depicts steps in a data acquisition method associated withaccountability and recovery, in accordance with the disclosedembodiments.

DETAILED DESCRIPTION

The particular values and configurations discussed in the followingnon-limiting examples can be varied, and are cited merely to illustrateone or more embodiments and are not intended to limit the scope thereof.

Example embodiments will now be described more fully hereinafter, withreference to the accompanying drawings, in which illustrativeembodiments are shown. The embodiments disclosed herein can be embodiedin many different forms and should not be construed as limited to theembodiments set forth herein; rather, these embodiments are provided sothat this disclosure will be thorough and complete, and will fullyconvey the scope of the embodiments to those skilled in the art. Likenumbers refer to like elements throughout.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used herein, thesingular forms “a”, “an”, and “the” are intended to include the pluralforms as well, unless the context clearly indicates otherwise. It willbe further understood that the terms “comprises” and/or “comprising,”when used in this specification, specify the presence of statedfeatures, integers, steps, operations, elements, and/or components, butdo not preclude the presence or addition of one or more other features,integers, steps, operations, elements, components, and/or groupsthereof.

Throughout the specification and claims, terms may have nuanced meaningssuggested or implied in context beyond an explicitly stated meaning.Likewise, the phrase “in one embodiment” as used herein does notnecessarily refer to the same embodiment and the phrase “in anotherembodiment” as used herein does not necessarily refer to a differentembodiment. It is intended, for example, that claimed subject matterinclude combinations of example embodiments in whole or in part.

Unless otherwise defined, all terms (including technical and scientificterms) used herein have the same meaning as commonly understood by oneof ordinary skill in the art. It will be further understood that terms,such as those defined in commonly used dictionaries, should beinterpreted as having a meaning that is consistent with their meaning inthe context of the relevant art and will not be interpreted in anidealized or overly formal sense unless expressly so defined herein.

It is contemplated that any embodiment discussed in this specificationcan be implemented with respect to any method, kit, reagent, orcomposition of the invention, and vice versa. Furthermore, compositionsof the invention can be used to achieve methods of the invention.

It will be understood that particular embodiments described herein areshown by way of illustration and not as limitations of the invention.The principal features of this invention can be employed in variousembodiments without departing from the scope of the invention. Thoseskilled in the art will recognize, or be able to ascertain using no morethan routine experimentation, numerous equivalents to the specificprocedures described herein. Such equivalents are considered to bewithin the scope of this invention and are covered by the claims.

The use of the word “a” or “an” when used in conjunction with the term“comprising” in the claims and/or the specification may mean “one,” butit is also consistent with the meaning of “one or more,” “at least one,”and “one or more than one.” The use of the term “or” in the claims isused to mean “and/or” unless explicitly indicated to refer toalternatives only or the alternatives are mutually exclusive, althoughthe disclosure supports a definition that refers to only alternativesand “and/or.” Throughout this application, the term “about” is used toindicate that a value includes the inherent variation of error for thedevice, the method being employed to determine the value, or thevariation that exists among the study subjects.

As used in this specification and claim(s), the words “comprising” (andany form of comprising, such as “comprise” and “comprises”), “having”(and any form of having, such as “have” and “has”), “including” (and anyform of including, such as “includes” and “include”) or “containing”(and any form of containing, such as “contains” and “contain”) areinclusive or open-ended and do not exclude additional, unrecitedelements or method steps.

The term “or combinations thereof” as used herein refers to allpermutations and combinations of the listed items preceding the term.For example, “A, B, C, or combinations thereof” is intended to includeat least one of: A, B, C, Aft AC, BC, or ABC, and if order is importantin a particular context, also BA, CA, CB, CBA, BCA, ACB, BAC, or CAB.Continuing with this example, expressly included are combinations thatcontain repeats of one or more item or term, such as BB, AAA, Aft BBC,AAABCCCC, CBBAAA, CABABB, and so forth. The skilled artisan willunderstand that typically there is no limit on the number of items orterms in any combination, unless otherwise apparent from the context.

All of the compositions and/or methods disclosed and claimed herein canbe made and executed without undue experimentation in light of thepresent disclosure. While the compositions and methods of this inventionhave been described in terms of preferred embodiments, it will beapparent to those of skill in the art that variations may be applied tothe compositions and/or methods and in the steps or in the sequence ofsteps of the method described herein without departing from the concept,spirit and scope of the invention. All such similar substitutes andmodifications apparent to those skilled in the art are deemed to bewithin the spirit, scope and concept of the invention as defined by theappended claims.

FIGS. 1-3 are provided as exemplary diagrams of data-processingenvironments in which embodiments of the present invention may beimplemented. It should be appreciated that FIGS. 1-3 are only exemplaryand are not intended to assert or imply any limitation with regard tothe environments in which aspects or embodiments of the disclosedembodiments may be implemented. Many modifications to the depictedenvironments may be made without departing from the spirit and scope ofthe disclosed embodiments.

A block diagram of a computer system 100 that executes programming forimplementing parts of the methods and systems disclosed herein is shownin FIG. 1. A computing device in the form of a computer 110 configuredto interface with sensors, peripheral devices, and other elementsdisclosed herein may include one or more processing units 102, memory104, removable storage 112, and non-removable storage 114. Memory 104may include volatile memory 106 and non-volatile memory 108. Computer110 may include or have access to a computing environment that includesa variety of transitory and non-transitory computer-readable media suchas volatile memory 106 and non-volatile memory 108, removable storage112 and non-removable storage 114. Computer storage includes, forexample, random access memory (RAM), read only memory (ROM), erasableprogrammable read-only memory (EPROM) and electrically erasableprogrammable read-only memory (EEPROM), flash memory or other memorytechnologies, compact disc read-only memory (CD ROM), Digital VersatileDisks (DVD) or other optical disk storage, magnetic cassettes, magnetictape, magnetic disk storage, or other magnetic storage devices, or anyother medium capable of storing computer-readable instructions as wellas data including image data.

Computer 110 may include or have access to a computing environment thatincludes input 116, output 118, and a communication connection 120. Thecomputer may operate in a networked environment using a communicationconnection 120 to connect to one or more remote computers, remotesensors, detection devices, hand-held devices, multi-function devices(MFDs), mobile devices, tablet devices, mobile phones, Smartphones, orother such devices. The remote computer may also include a personalcomputer (PC), server, router, network PC, RFID enabled device, a peerdevice or other common network node, or the like. The communicationconnection may include a Local Area Network (LAN), a Wide Area Network(WAN), Bluetooth connection, or other networks. This functionality isdescribed more fully in the description associated with FIG. 2 below.

Output 118 is most commonly provided as a computer monitor, but mayinclude any output device. Output 118 and/or input 116 may include adata collection apparatus associated with computer system 100. Inaddition, input 116, which commonly includes a computer keyboard and/orpointing device such as a computer mouse, computer track pad, or thelike, allows a user to select and instruct computer system 100. A userinterface can be provided using output 118 and input 116. Output 118 mayfunction as a display for displaying data and information for a user,and for interactively displaying a graphical user interface (GUI) 130.

Note that the term “GUI” generally refers to a type of environment thatrepresents programs, files, options, and so forth by means ofgraphically displayed icons, menus, and dialog boxes on a computermonitor screen. A user can interact with the GUI to select and activatesuch options by directly touching the screen and/or pointing andclicking with a user input device 116 such as, for example, a pointingdevice such as a mouse and/or with a keyboard. A particular item canfunction in the same manner to the user in all applications because theGUI provides standard software routines (e.g., module 125) to handlethese elements and report the user's actions. The GUI can further beused to display the electronic service image frames as discussed below.

Computer-readable instructions, for example, program module or node 125,which can be representative of other modules or nodes described herein,are stored on a computer-readable medium and are executable by theprocessing unit 102 of computer 110. Program module or node 125 mayinclude a computer application. A hard drive, CD-ROM, RAM, Flash Memory,and a USB drive are just some examples of articles including acomputer-readable medium.

FIG. 2 depicts a graphical representation of a network ofdata-processing systems 200 in which aspects of the present inventionmay be implemented. Network data-processing system 200 is a network ofcomputers or other such devices such as mobile phones, smartphones,sensors, detection devices, and the like in which embodiments of thepresent invention may be implemented. Note that the system 200 can beimplemented in the context of a software module such as program module125. The system 200 includes a network 202 in communication with one ormore clients 210, 212, and 214, and external device 205. Network 202 mayalso be in communication with one or more RFID and/or GPS enableddevices or sensors 204, servers 206, and storage 208. Network 202 is amedium that can be used to provide communications links between variousdevices and computers connected together within a networked dataprocessing system such as computer system 100. Network 202 may includeconnections such as wired communication links, wireless communicationlinks of various types, fiber optic cables, quantum, or quantumencryption, or quantum teleportation networks, etc. Network 202 cancommunicate with one or more servers 206, one or more external devicessuch as RFID and/or GPS enabled device 204, and a memory storage unitsuch as, for example, memory or database 208. It should be understoodthat RFID and/or GPS enabled device 204 may be embodied as a mobiledevice, cell phone, tablet device, monitoring device, detector device,sensor microcontroller, controller, receiver, transceiver, or other suchdevice.

In the depicted example, RFID and/or GPS enabled device 204, server 206,and clients 210, 212, and 214 connect to network 202 along with storageunit 208. Clients 210, 212, and 214 may be, for example, personalcomputers or network computers, handheld devices, mobile devices, tabletdevices, smartphones, personal digital assistants, microcontrollers,recording devices, MFDs, etc. Computer system 100 depicted in FIG. 1 canbe, for example, a client such as client 210 and/or 212.

Computer system 100 can also be implemented as a server such as server206, depending upon design considerations. In the depicted example,server 206 provides data such as boot files, operating system images,applications, and application updates to clients 210, 212, and/or 214.Clients 210, 212, and 214 and RFID and/or GPS enabled device 204 areclients to server 206 in this example. Network data-processing system200 may include additional servers, clients, and other devices notshown. Specifically, clients may connect to any member of a network ofservers, which provide equivalent content.

In the depicted example, network data-processing system 200 is theInternet with network 202 representing a worldwide collection ofnetworks and gateways that use the Transmission ControlProtocol/Internet Protocol (TCP/IP) suite of protocols to communicatewith one another. At the heart of the Internet is a backbone ofhigh-speed data communication lines between major nodes or hostcomputers consisting of thousands of commercial, government,educational, and other computer systems that route data and messages. Ofcourse, network data-processing system 200 may also be implemented as anumber of different types of networks such as, for example, an intranet,a local area network (LAN), or a wide area network (WAN). FIGS. 1 and 2are intended as examples and not as architectural limitations fordifferent embodiments of the present invention.

FIG. 3 illustrates a software system 300, which may be employed fordirecting the operation of the data-processing systems such as computersystem 100 depicted in FIG. 1. Software application 305, may be storedin memory 104, on removable storage 112, or on non-removable storage 114shown in FIG. 1, and generally includes and/or is associated with akernel or operating system 310 and a shell or interface 315. One or moreapplication programs, such as module(s) or node(s) 125, may be “loaded”(i.e., transferred from removable storage 114 into the memory 104) forexecution by the data-processing system 100. The data-processing system100 can receive user commands and data through user interface 315, whichcan include input 116 and output 118, accessible by a user 320. Theseinputs may then be acted upon by the computer system 100 in accordancewith instructions from operating system 310 and/or software application305 and any software module(s) 125 thereof.

Generally, program modules (e.g., module 125) can include, but are notlimited to, routines, subroutines, software applications, programs,objects, components, data structures, etc., that perform particulartasks or implement particular abstract data types and instructions.Moreover, those skilled in the art will appreciate that elements of thedisclosed methods and systems may be practiced with other computersystem configurations such as, for example, hand-held devices, mobilephones, smart phones, tablet devices, multi-processor systems, printers,copiers, fax machines, multi-function devices, data networks,microprocessor-based or programmable consumer electronics, networkedpersonal computers, minicomputers, mainframe computers, servers, medicalequipment, medical devices, and the like.

Note that the term module or node as utilized herein may refer to acollection of routines and data structures that perform a particulartask or implements a particular abstract data type. Modules may becomposed of two parts: an interface, which lists the constants, datatypes, variables, and routines that can be accessed by other modules orroutines; and an implementation, which is typically private (accessibleonly to that module) and which includes source code that actuallyimplements the routines in the module. The term module may also simplyrefer to an application such as a computer program designed to assist inthe performance of a specific task such as word processing, accounting,inventory management, etc., or a hardware component designed toequivalently assist in the performance of a task.

The interface 315 (e.g., a graphical user interface 130) can serve todisplay results, whereupon a user 320 may supply additional inputs orterminate a particular session. In some embodiments, operating system310 and GUI 130 can be implemented in the context of a “windows” system.It can be appreciated, of course, that other types of systems arepossible. For example, rather than a traditional “windows” system, otheroperation systems such as, for example, a real time operating system(RTOS) more commonly employed in wireless systems may also be employedwith respect to operating system 310 and interface 315. The softwareapplication 305 can include, for example, module(s) 125, which caninclude instructions for carrying out steps or logical operations suchas those shown and described herein.

The following description is presented with respect to embodiments ofthe present invention, which can be embodied in the context of, orrequire the use of a data-processing system such as computer system 100,in conjunction with program module 125, and data-processing system 200and network 202 depicted in FIGS. 1-3. The present invention, however,is not limited to any particular application or any particularenvironment. Instead, those skilled in the art will find that thesystems and methods of the present invention may be advantageouslyapplied to a variety of system and application software includingdatabase management systems, word processors, and the like. Moreover,the present invention may be embodied on a variety of differentplatforms including Windows, Macintosh, UNIX, LINUX, Android, Arduinoand the like. Therefore, the descriptions of the exemplary embodiments,which follow, are for purposes of illustration and not considered alimitation.

In the embodiments herein, a system, method, and apparatus for fosteringrecovery and accountability is disclosed. The embodiments have two basicpurposes. The first, is to provide an interactive, real timerelationship between a user and their accountability partner or manager,through the disclosed systems, to provide the user the tools necessaryto learn to be accountable to themselves. In certain embodiments, themethods and systems can be used by those coming out of correctionsfacilities and entering drug or alcohol rehabilitation programs to meettheir legal requirements and/or aftercare responsibilities. However, inother embodiments, use cases can include other situations or socialstructures where a client/employee/patient is responsible for being in avariety of locations at different times, and where there is anaccountability partner who wants or needs to verify attendance at theseappointments.

FIG. 4 illustrates a block diagram of a system 400 for teachingcompliance and accountability. The system can generally include a mobiledevice, or user device 405 that provides a user portal 410. The userportal 410 can serve as the interface through which the patient (oruser) interacts with the system 400.

As illustrated in FIG. 4, the user device 400 can be any device that cantake screenshots and is equipped with a camera 415, and has a GPSreceiver 420, such that the device 405 can verify position and time. Incertain embodiments, the user device 405 can comprise a mobile device,or smart phone, a tablet device, a computer, a smart watch, or othersuch device.

The user device 405 can be equipped with a user portal 410. In certaincases, the user portal 410 can comprise a standalone software module(e.g. an app). In other embodiments, the user portal 410 can be a webportal. The user portal 410 serves as the interface through which theuser interacts with the compliance and accountability system 400. Theinterface can comprise a specially designed graphical user interfacethat allows the user to receive alerts relating to scheduling, andverify that the user has complied with a given requirement. This can beachieved in a number of ways as further detailed herein.

The mobile device 405 can interact with other aspects of the systemthrough a wired or wireless connection via the world wide web. Incertain embodiments, this can be achieved using a cloud computingarchitecture. In certain embodiments, a server 425 can provide data 435storage and can provide an accountability module 430.

The system 400 further includes a partner device 440. The partner device440 can comprise a mobile device, or smart phone, a tablet device, acomputer, a smart watch, or other such device. The partner device 440can be equipped with a partner portal 445. The partner portal 445 servesas the interface through which the partner interacts with the complianceand accountability system 400. An interface associated with the partnerportal 445 can comprise a specially designed graphical user interfacethat allows the partner to set and receive alerts relating toscheduling, monitor user compliance, send messages to a user, andmonitor success metrics. It should be understood that the partner device440 can comprise multiple devices accessible by multiple partners. Suchaccess can be hierarchical as further detailed herein.

The accountability module 430 can comprise the root application (orsoftware) that is used to control the system. The server 425 can servedata to, and accept data from, the user device 405 and partner device440. In other embodiments, cloud storage 450 can be used to store someor all of the relevant data and/or software associated with the system400.

FIG. 5 illustrates a system diagram of the accountability module 430.The accountability module 430 can include a calendar module 505 that isat the core of the system 400. The calendar module 505 can be connectedto a partner input 530 associated with the partner device 440. Note thisinput can comprise a hardwired or wireless communications connection.

The calendar module 505 can be used to set various appointments for theuser. In an exemplary embodiment, the calendar module 505 can beaccessed by the partner device 440. The partner can schedule variousappointments in a calendar associated with the calendar module 505. Suchappointments can be, for example, a parole meeting, a 12 step meeting, atherapy session, a group therapy session, etc. The calendar module 505can include data fields in a structured database indicative of the typeof appointment, the time of the appointment, and the location of theappointment. In certain embodiments, the accountability module 430 canuse the location of the appointment to create a geofence indicative of areal world location associated with the location of the appointment. Thepartner can set the parameters of the geofence. For example, thegeofence can be a set size or location. The structured database can alsoinclude a field that allows the partner to identify an appointment asmandatory or suggested. The calendar module 505 can then populate aninteractive calendar provided on the user device via the user portal410. Modifications to the calendar made by the partner on the partnerdevice 440 can update the calendar provided via the user portal 410.

The accountability module 430 can further include a resource module 510.The resource module 510 can comprise a list of resources available tothe user. The list can be sorted manually by the partner via theresource module 825 in the partner portal 445, to provide thoseresources most applicable to a given user nearer to the top of the list.The list can also be automatically sorted according to data taken fromthe calendar module 505. For example, the resource module 510 can adjustthe resources list to identify resources related to counseling, when thenext appointment on the calendar is a therapy session. The resourcemodule 510 can then serve the resource list to the user device 405 fordisplay in the user portal 410 via resource module 625.

The accountability module 430 can further include a data analyticsmodule 515 that can be used to collect and sort data associated witheach user. The following is an exemplary explanation of ways the data inthe system 400 is cultivated, stored, and transmitted. The chartsprovided below (charts 1-5) show a 9×5 table of data, but other metricscan be used in other embodiments which would change the number of cellsin the table. Fixed and variable appointments can be part of event typeas one item. Thus, for each user a 9×4 dataset is developed, though theexemplary grids show 9×5.

A hierarchical system of data distribution are a part of the system 400that allows partners to evaluate the metrics of those in lower tiers ofthe hierarchy. The hierarchical scheme 1100 is illustrated in FIG. 11.As illustrated, a series of hierarchical access layers provide accesscontrol to various data. The access layers can include Super user layer1105, Super administrator layer 1110, administrator layer 1115, partnerlayer 1120, and user layer 1125.

In an exemplary embodiment, a superuser in the super user layer 1105 canadd a superadmin in the super administrator layer 1110, administratorsin the administrator layer 1115, managers in the partner layer 1120, andclients in the user layer 1125. Likewise, Superadmins can addadministrators, managers, and clients. Administrators can add otheradministrators, managers and clients. Managers can ONLY add clients.Clients can ONLY access their own data, and cannot amend, change, ordelete it. Further client's in the user layer 1125 can, for example, addtheir own calendar items but can only delete or amend items they haveadded themselves.

As illustrated in the charts 1-5 various metrics associated with userbehavior can be collected. Those metrics can, for example be based on 9categories, with 4 cross referencing categories. These can includeappointments required; number made; percentage of total made; andaggregating total made. Every client in the user layer 1125 can see onlytheir own data.

Manager metrics aggregate the total metrics of all clients in the userlayer 1125 working with a given manager in the partner layer 1120, intoa set of metrics for that manager based on the same criteria. Thus, eachmanager in the partner layer 1120 will have access to individual dataand aggregated data for their clients. The manager can access theirtotal metrics and their individual clients' metrics.

Administrators in the administrator layer 1115 can have access to thesame categories, but can also have access to aggregated data for everymanager in the partner layer 1120, under that administrator. Similarly,superadmins in the super administrator layer 1110, can access the same9×4 categories, but can also access aggregate data for everyadministrator in the administrator layer 1115 under that superadmin. Itshould be noted that certain organization may not have or need one ormore of the layers such as the super administrator layer 1110.

The Superuser can access aggregate data totals from all the layers usingthe system 400. Over time, the data can be segregated into: data bygeographical areas; data by organization types (judicial, health care,education); organizations within types (one health insurance company v.another insurance company, etc.). Data aggregation can be flexible andexpandable. Ideally, metrics can be based on industry type, andgeographical area (city, county, state). It may be that the rollup fromcity to county to state is analogous to the rollup from manager toadministrator to superadmin.

CHART 1 Client sees only his data 12 step variable required made % totalPO/judicial fixed

Test variable individual fixed Group fixed Community variable serviceMedical fixed School/work variable Other fixed

indicates data missing or illegible when filed

CHART 2 Manager sees client, all of her clients 12 step variablerequired made % total PO/judicial fixed

Test variable individual fixed Group fixed Community variable serviceMedical fixed School/work variable Other fixed

indicates data missing or illegible when filed

CHART 3 Administrator sees all clients, all managers 12 step variablerequired made % total PO/judicial fixed

Test variable individual fixed Group fixed Community variable serviceMedical fixed School/work variable Other fixed

indicates data missing or illegible when filed

CHART 4 SuperAdministrator sees all clients, managers, administrators 12step variable required made % total PO/judicial fixed

Test variable individual fixed Group fixed Community variable serviceMedical fixed School/work variable Other fixed

indicates data missing or illegible when filed

CHART 5 Superuser Sees all 12 step variable required made % totalPO/judicial fixed

Test variable individual fixed Group fixed Community variable serviceMedical fixed School/work variable Other fixed

indicates data missing or illegible when filed

In certain embodiments, the data can be represented as athree-dimensional data model with the X- and Y-axes used to build the9×4 grid, with Y-axis representing up to nine stipulations with whichthe client is asked to comply, and the X-axis representing ways tomeasure compliance. The Z-axis represents layers of data aggregation:client, manager, administrator (and super-administrators, as needed).

It is important to appreciate that data as outlined above, can populatedata structures in accordance with charts 1-5. All the data is derivedfrom client action. Aggregation across data sets allows administratorsto work with client data in a variety of ways. The resulting informationcan be used for comparing compliance. For example, the data willillustrate that a given client attends testing but not meetings, ormeetings but not group therapy, etc. The system 400 can thus be used topinpoint for example, that manager A has clients who consistently go tomeetings but not group, or that Manager B has clients who consistentlyoutperform or underperform other managers' clients.

Superuser data can integrate—for the first time—bona fide aftercarestatistics between and among healthcare and correctional contexts. Inthis way the system 400 can be used to track a client in and through thejudicial and medical systems, to be able to see clearly “what works” andat what point a client shifts into compliance and recovery even afterlong periods of non-compliance and/or recidivism.

Aggregated data, populated in the data structures further allowsmanagers to see, via the partner portal 445, how their clients are doingholistically, and allows managers and administrators to identifyoutliers—positive and negative—overall or among any of the variablesillustrated in Charts 1-5 (i.e. along the Y-axis). In this way,administrators are able to evaluate the overall success of their programas a whole. In particular, they can make the meaningful assessments oftheir managers, pinpointing particular areas along the Y-axis wherein agiven manager's clients are outliers, positive or negative—and to assessoverall how and whether particular managers' clients are doingparticularly well or poorly, again, in real time.

Metrics can be collected from the user device via the user portal 410and can then be transferred to cloud storage 450 for cloud-based dataaggregation. Such storage can be associated with the server 425. Datacan be delivered to the user portal 410 and partner portal 445 via theaccountability module 430, where the calendar is established, updatedand maintained, and where user compliance is verified.

The user portal 410 serves as the interface through with the userinteracts with the accountability system 400 and is further illustratedin FIG. 6. The user portal 410 can be embodied as specially designedsoftware that is executed by a mobile device or other computer systemsuch as computer system 100. The user portal 410 can include a userinterface embodied as a graphical user interface, such as GUI 130. Theuser portal 410 allows the user to interact with the calendar module605. The interface 130 can display upcoming appointments, and identifythose appointments as mandatory or suggested, according to thedesignation entered by the partner via the calendar module 505. The userinterface can inform the user of the type, time, and place of theappointment.

An alerts module 610 can be used to alert the user to upcomingappointments. The alerts module 610 can send push notifications, orother such notification to alert a user that an appointment is upcoming,or that the appointment has been missed. The alerts module 610 cansimilarly send an alert to the partner when an appointment is missed.

The user portal can further include a user sign-in module 615. The usersign-in module is a critically important feature of the presentembodiments. The user sign-in module 615, is a cornerstone of theaccountability system 400 that allows the system 400 to operation a waythat would not be possible with standard human verification approaches.The user sign-in module 615 can be used to verify that the user hasattended an appointment or has otherwise met the requirement of being ata specific place at a specific time. Upon reaching the designatedlocation of the appointment, the user device 405 can check the locationof the user with the GPS receiver 420, or via location servicesassociated with the user device 405. The user sign-in module 615 canverify the user is currently within the geofence, or otherwise generallyat the location, for the appointment established by the partner. Theuser can next be prompted to take a photograph of themselves. Thephotograph, along with the user's location, and time, can be recordedand transmitted to the accountability module 430 as a check-in.

When the appointment ends, the user can similarly take a photograph ofthemselves using the camera 415 associated with the user device 405. Thephotograph, along with the user's location, and time can be recorded andtransmitted to the accountability module 430 as a check-out.

The accountability module 430 can verify the check-in and check-out dataagainst the appointment data. For example, the accountability module 430can verify that the check-in time was within a preset threshold of theappointment start time, and that the check-out time was within a presetthreshold of the appointment end time.

The accountability module 430 can include biometrics verificationsoftware module 525 that can compare the check-in photograph and thecheck-out photograph against a pre taken photograph, to ensure that theperson in the photograph is the user. The system can use facialrecognition software, to verify the face in the photograph matches thepreviously saved image. Similarly, the accountability module 430 canverify that the check-in location is within the geofence established bythe partner, and that the check-out location is within the geofenceestablished by the partner. In certain embodiments, the user device 405can further indicate information associated with the network connectionused to transmit the check-in and check-out data. The accountabilitymodule 430 can verify that the network connection information used totransmit the check-in and check-out data matches the network connectioninformation at the check-in and check-out location. It should beappreciated that the check-in and check-out locations can be selected tonot be identical if necessary.

Once the accountability module 430 receives the user data at a userinput 520, associated with the check-in and check-out data, the data canbe provided to the data analytics module 515. The accountability module430 can update the user's calendar module 605 to indicate that the usersuccessfully kept the appointment, partially kept the appointment, ormissed the appointment. The calendar module 605 can update the userachievement module 620 to create a log, viewable by the user, of thesuccessful completion of various appointments. The appointments can becolor coded in the user achievement module. For example, successfullycompleted appointments can be coded green, partially completedappointments can be coded yellow, and missed appointments can be codedred. For suggested appointments, only successfully completedappointments can be displayed in the user achievement module 620.

FIGS. 7A-7H illustrate screen shots of a user portal interface 700 inaccordance with an exemplary embodiment of the system 400. It should beappreciated that these represent one embodiment of the user portalinterface 700, and that the user portals 410 could be embodied withother user interfaces 700.

FIG. 7A illustrates a user home screen 705. The user home screen 705 canprovide access buttons to a user dashboard 710, a calendar 711, and thesign in module 712. The user home screen 705 can further include asidebar of links 715 to the home screen the dashboard the sign in/ signout module and the calendar module. FIG. 7B further illustrates anupcoming appointments reminder 720 that can be provided on the homescreen 705. The upcoming appointments reminder 720 can be generated bythe alarm module 610 and can include a list of appointments upcoming forthe day. The reminders 720 can include the type of appointment, the timeof the appointment, and a check box 721 where the user can acknowledgereceipt of the reminder.

The acknowledgement check is an important tool for addressingaccountability and preventing relapse. In many cases a relapse is not acatastrophic single day event. Instead, relapse is generally a result ofmissing a first appointment, and then a second, and then ignoringseveral appointments, until all such accountability is dismissed.

The acknowledgement check box 721 is configured to require the user toacknowledge each appointment scheduled in a given day. For many usersthis will include multiple appointments on that day. The acknowledgementcheck box 721 can be linked to the partner portal 445. In an exemplarycase, the user can check the acknowledgement check box 721 toacknowledge various appointments are scheduled for the day. If the useracknowledges the appointments, that information is transmitted to thepartner. However, if the user does not acknowledge appointments for aday, a flag can be provided to the partner. If the user does notacknowledge appointments for a series of days, the flag provided to thepartner can escalate from, for example, a yellow status to a red status.

In situations where the partner is managing many users every day, it isimpossible for the manager to physically contact each user every day toverify that they are aware of their appointments. However, theacknowledgment check box 721 allows the partner to see users who havefailed to acknowledged appointments, immediately. Failing to acknowledgeappointments can serve as an early warning sign to the partner ofpotential relapse (as opposed to an update at a monthly in personmeeting which is too late to help prevent the relapse), and helps tohold the user accountable for their appointments.

FIG. 7C includes a weekly progress report 725 provided on the user'shome screen 705. The weekly progress report 725 can include a colorcoded indication 726 of compliance with a selection of appointmenttypes. In FIG. 7C the appointments provided in the weekly progressreport 725 include: 12 step program (color coded blue),judicial/probation (color coded red), testing (color coded yellow),individual counseling (color coded green), group counseling (color codedorange), community service (color coded light blue), medical (colorcoded purple), work/school (color coded brown), and other (color codedblack). It should be appreciated that these appointment types areexemplary and in other contexts other appointment type can be used.

The color coding is an important feature of the weekly progress report725. For many users, literacy may be an issue. Color coding allowsilliterate users to identify the various appointment types. The colorcoding can be consistent throughout the various modules of the platform.

The weekly progress report 725 can provide an indication 727 of whetherthe appointment type is “variable” or “fixed”. A variable typeappointment indicates that the user can complete the task at theirconvenience. For example, a user may be required to perform 10 hours ofcommunity service a week. The user can complete those hours at whatevertime/day/place they choose—therefore the appointment type is variable. Afixed appointment refers to an appointment type that includes specifictime and place requirements. For example, a medical appointment with adoctor must be completed at a specific time and place—and is therefore afixed appointment type.

The weekly progress report 725 can include two indicator bars for eachprogram type. The first indicator bar 728 for the appointment typeindicates the number of appointments of that type that are required forthe week. The bar can fill to indicate completion of the appointmenttype as the user completes appointments. For example, the user may berequired to attend 5 twelve step meetings each week. The progressindicator bar 728 can show that 5 such meetings are required. When theuser attends a meeting and properly verifies attendance with the system,the indicator bar can fill ⅕ of the way and a numeric indicator that 4meetings are left can be provided.

The second indicator bar 729 can be a lifetime attendance count for theappointment type. Every time that the user attends that appointment typethe associated indicator bar can increase by one. This lifetimeindicator bar 729 is a means of positively reinforcing the user'sattendance at required appointments. The weekly progress report 725 canfurther provide an “All Time Total” 730 that graphically illustrateslifetime totals for each of the appointment types. Research suggestspositive reinforcement of long term accountability improves a user'sability to become self-accountable.

FIG. 7D illustrates a screen shot of the user home screen 705, that caninclude a past appointments notification 735. This screen can notify theuser of any missed appointments that day, and as a reward, can alsoindicate successfully attended appointments.

FIG. 7E illustrates a chart 740 of weekly bonus appointments, that canbe provided on the home screen 705 of the user portal 410. The weeklybonus appointments are color coded with the appointment types previouslyprovided in the weekly progress report. Bonus appointments represent,non-requisite appointments, that the user attended beyond thoserequired. For example, if a user is required to attend 5 twelve stepmeetings a week, but attends one every day, for a total of sevenmeetings, attendance at the last two meetings can be memorialized bygold stars (or other such positive feedback indicator) on the weeklybonus appointments chart 740. The weekly bonus appointments chart 740allows the user to catalog the steps the user is taking beyond thoserequired, in order to positively reinforce the user'sself-accountability.

FIG. 7F illustrates the user interface 745 for the sign-in module 615 inaccordance with the disclosed embodiments. It should be appreciated thatthis module 615 can be used to sign-in and sign-out of an appointment asa means for verifying attendance at an appointment.

As illustrated, once the user is at the appointment the user can use adrop down menu 750 to identify the appointment type. The user can alsoenter a name for the appointment in the text entry field 751. Next, theuser is prompted to take a photograph of themselves. Button 752 can beused to capture a photograph. The photograph can include metadata thatindicates the location where the photograph was taken and the time whenthe photograph was taken. This can used to prevent fraudulent uploads ofphotos taken at a different place or time, but held out as evidence ofcheck-in at the required appointment. Once the photo is uploaded apreview can be provided in window 753, at which point the user cansubmit the check-in with button 754.

After the appointment, the user can similarly be prompted to take aphotograph of themselves. The photograph can include metadata includingthe location and time where the photograph was taken. This can be usedto verify that the user attended the appointment.

FIG. 7G illustrates the user interface 755 associated with the usercalendar module 605. The calendar module 605 provides a calendar view760 of the user's appointments for the given month. For example, thecalendar module 605 can provide color coded dots, the color codingmatching that of the weekly progress report 725, that provides anindication of the day and time of each of the appointments for the user.The interface 755 can include an indicator of whether the user isinteracting with appointments on the current day and allows the user tonavigate between days. The calendar can provide an option 761 to selecta month overview, as shown in FIG. 7G, a week long view, a 3 day view,or a single day view.

When the user interacts with the interface in the calendar view 760,hovering over or clicking a given day can provide a list of theappointments for that day as illustrated at 762. If the user selects anappointment, an information bar 763 can be displayed showing the detailsrelated to that appointment, including whether the appointment is fixedor variable, the type of appointment, the time of the appointment, andthe location of the appointment.

The calendar view 760 also provides a button 764 to allow the user tocreate a new requirement. The addition of a new requirement can beprovided in the user interface screen 765 as illustrated in FIG. 7H.This screen includes drop down menu 766 that allows the user to select atype of meeting and a menu 767 for setting the date of the appointment.The user can further use radio button 768 to indicate if the meetingtype is fixed or variable. The user can use text field 769 to indicatethe time of the meeting or can use check box 770 to indicate theappointment can be met anytime. A checkbox 771 is provided to indicateif the appointment is recurring. When the requirement is submitted withbutton 772, the requirement will automatically populate as a newappointment in the calendar and on the weekly progress report.

FIG. 8 illustrates a partner or manager portal 445 in accordance withthe disclosed embodiments. The manager or partner portal 445 serves asthe interface through which the partner interacts with theaccountability system 400. The partner portal 445 can be embodied asspecially designed software that is executed by a mobile device or othercomputer system such as system 100. The partner portal 445 can include apartner interface embodied as a graphical user interface. The partnerinterface allows the partner to interact with the calendar module 805and to view analytics for all the users the partner is managing. Theinterface can display upcoming appointments, and identify thoseappointments as mandatory or suggested, according to the designationentered by the partner. The partner interface can inform the partner ofthe type, time, and place of appointments for all the users the partneris managing.

An alerts module 810 can be used to alert the partner to upcomingappointments. The alerts module 810 can send push notifications, orother such notification to alert a partner that a user appointment isupcoming, or that the user missed an appointment. The alerts module 810can further receive notice to alert the partner of an appointment thathas been missed.

The partner portal 445 can further include a partner review module 815that can be used to track data metrics, as illustrated in charts 1-5,for all the users the partner is managing. The partner review module 815allows the partner to see analytics for each user that indicates theusers' successful attendance at required appointments, missedappointments, attendance at bonus appointments, etc. The partner reviewmodule 815 can include partner-set flags that trigger notifications tothe partner when a user misses a preset number of appointments, when auser is late to a certain number of appointments, when the user fails toacknowledge one or more appointments for a certain number of days, etc.

Once the accountability module 430 receives the user appointment at auser input, associated with the check-in and check-out data, the datacan be provided to the data analytics module 515. The accountabilitymodule 430 can update the user's calendar module 605 to indicate thatthe user successfully kept the appointment, partially kept theappointment, or missed the appointment. The calendar module 605 canupdate the user achievement module 820 viewable in the partner portal445 to create a log, viewable by the partner, of the successfulcompletion of various appointments. The appointments can be color codedin the user achievement module. For example, successfully completedappointments can be coded green, partially completed appointments can becoded yellow, and missed appointments can be coded red. For suggestedappointments, only successfully completed appointments can be displayedin the user achievement module 820.

FIGS. 9A-9I illustrate screen shots of an interface 900 associated witha partner or manager portal 445 in accordance with an exemplaryembodiment of the system 400. It should be appreciated that thesefigures represent one embodiment of the interface 900 associated withmanager or partner portal 445 and that the partner portal 445 can beembodied with other user interfaces in other embodiments.

As with the user portal, the partner portal 445 allows the user'srecovery partner or manager to monitor the accountability metrics of theuser remotely, so that the manager can reward the user for positiveperformance, and intervene quickly when the accountability metricsindicate the user is at risk (e.g. at risk of relapse).

The partner portal 445 can include a home page 905 as illustrated inFIG. 9A. The home page 905 provides the partner a list 906 of users thepartner is managing. The home screen 905 of the partner portal 445includes button 907 allows the manager to add new users as they becomeusers of the accountability system 400.

The manger can select one of the users (or clients) from the list 906 ofclients the manager is managing. FIG. 9B illustrates a selection oflinks the manager can select for each user they manage. The links caninclude progress link 910, a calendar module link 911, the ability toadd requirements via a requirements link 912, and a user sign in check913. In FIG. 9B, the sign in check 913 is illustrated as selected. Thesign in check 913 allows the manager or partner review a list 914 allthe verified sign ins for the selected user.

FIG. 9C illustrates a view of the home page after one of the users hasbeen selected from the list 906 by the manager. In FIG. 9C the progresslink 910 is illustrated as selected. A weekly progress report 915,similar to the reported provide to the user on the user's home screencan be illustrated in the manager portal 445. The weekly progress report915 can include a color coded indication 919 of compliance with aselection of appointment types. In FIG. 9B the appointments include: 12step program (color coded blue), judicial/probation (color coded red),testing (color coded yellow), individual counseling (color coded green),group counseling (color coded orange), community service (Color codedlight blue), medical (color coded purple), work/school (color codedbrown), and other (color coded black). It should be appreciated thatthese appointment types are exemplary, and in other contexts otherappointment type can be used, where the appointment types will matchthose shown to the associated user in the user's module.

The weekly progress report 915 can provide an indication 916 of whetherthe appointment type is “variable” or “fixed”. The weekly progressreport 915 can include two indicator bars for each program type. Thefirst indicator bar 917 for the appointment type indicates the number ofappointments of that type that are required for the week. The bar 917can fill to indicate completion of the appointment type as the usercompletes appointments. The second indicator bar 918 can be a lifetimeattendance count for the appointment type for the selected user. Everytime that the user attends that appointment type the associatedindicator bar can increase by one.

As with the user portal, the partner or manager portal 445 can alsoprovide a view 920 of a list 921 weekly bonus appointments attended bythe selected user as illustrated in FIG. 9D.

The manager or partner portal 445 can further include a compliancereport 925 for each of the users managed by the partner. The compliancereport 925 can be configured by the manager to illustrate complianceover a selected period of time. In the embodiment illustrated in FIG. 9Ethe compliance is illustrated over a week.

The compliance report 925 can include a list 926 of all of the requiredappointments for the user over the selected period of time. A redindicator can be used to identify requirements not met by the user. Agreen indicator can indicate requirements met by the user. Thecompliance report 925 provides the manager a quick reference fordetermining if the user is meeting requirements. As the user completesvarious tasks and/or attends appointments (verified by the sign inmodule) the compliance report 925 can be updated to indicate that theuser has met requirements.

FIG. 9F illustrates calendar view 930 associated with the calendarmodule 805 as it can be presented in the manager or partner portal 445.The calendar module 805 provides a calendar view 930 of the user'sappointments for a given month. For example, the calendar module 805 canprovide color coded dots, the color coding matching that of the weeklyprogress report, that provides an indication of the day and time of eachof the appointments for the selected user. The interface can include anindicator of whether the user is interacting with appointments on thecurrent day and allows the partner to navigate between days. Thecalendar can provide an option 931 to select a month overview, as shownin FIG. 9F, a week long view, a 3 day view, or a single day view.

FIG. 9G illustrates a view 940 of a GUI associated with the partnermodule 445 that allows the partner to create a new requirement. Thisscreen includes a drop down menu 941 that allows the partner to select atype of meeting and field 942 to enter the date of the appointment. Thepartner can further indicate if the meeting type is fixed or variablewith field 943. The partner can specify a time of the appointment atfield 944 or can check box 945 if the requirement can be met anytime.The partner can check box 946 if the appointment is recurring. When therequirement is submitted using button 947, the requirement willautomatically populate as a new appointment in the calendar of the userand the partner, and on the weekly progress report for the user and thepartner.

FIG. 9H illustrates a compliance report view 950 associated with thepartner module 445. The compliance report view 950 provides a list 951of compliance checks that the partner can use to monitor the complianceof the user. The compliance report view 950 can include a color codedlist 951 of requirement types. For each of the requirements, thecompliance report can include an indicator 952 of the type ofrequirement, an indicator 953 of the date/time associated with therequirement. The report can include an indicator 954 of the requirementbeing compulsory or a bonus, an indicator 955 of a sign-in start time,an indicator 956 of variance, an indicator 957 of the duration betweenthe sign in and sing out time, an indicator 958 of the compliancestatus, and an indicator 959 of the client name. The compliance reportview 950 can be organized as a list of all outstanding requirements fora given period of time (i.e. a week). The compliance report view 950gives the partner/manager the ability to quickly verify if the user isin compliance with their weekly requirements.

FIG. 9I illustrates a user status view 960, viewable by the manager. Theuser status interface view 960 can give the manager the ability tomanage various administrative aspects of the system 400. It should beappreciated that this and other aspects of the system 400 that requireconfidentiality can be configured to ensure they are compliant withvarious data and record keeping rules for health records, such as theHealth Insurance Portability and Accountability Act.

The user status interface view 960 can include the user status 961, username 962, user email address 963, role 964, date of creation 965, and anindication of whether the user has verified their account via email 966.From this screen the manager can deactivate the user account with button967. In addition, the manager can delete all user requirements usingbutton 968. However, because this action will erase all userrequirements, it can be verified with a verification that the mangerwants to delete all the requirements, before final removal of all therequirements.

FIG. 10 illustrates a analytics interface 1000 that provides analyticscollected at any hierarchical level. The analytics can be used todetermine the efficacy of the user as compared to others at anequivalent hierarchical layer using the system 400. As illustrated inFIG. 10, the analytics interface 1000 can illustrate various metrics foreach of the requirements. For example, for each of the requirementtypes, the analytics interface 1000 can show the total completedrequirements 1005 for all those being managed by the manger, and thebonus requirements 1010 completed. The interface can further show thetotal number of requirements 1015 and the percentage of completedrequirements 1025. The analytics interface can further show the totalnumber of non-compliant user's 1020 being managed by the manager. Thisinformation can be provided for each requirement type and total metricsacross all requirement types can be provide.

FIGS. 4-10 illustrate various components and interfaces of the system400. The following illustrates various features and methods associatedwith the system 400 disclosed in FIGS. 4-10. The system 400 can operatewithin a context of systems—not only data systems, but behaviormodification systems.

Thus, in an embodiment the system 400 can provide a digital platformthat helps the process of evolution by ensuring that people and agencieshave means and mechanisms to follow through on the decision to changeand implement the choices they make. The system 400 eliminatesfalsification, manipulation, coercion and requires the client to beaccountable for him or herself.

FIG. 12 illustrates a method 1200 associated with the system 400disclosed herein for accountability and compliance. The order of stepsillustrated in this method 1200 are exemplary and associated methods caninclude a rearrangement of the order of these steps without departingfrom the scope of embodiments disclosed.

The method 1200 being at step 1205. In an exemplary embodiment, a usercan register and create an account. The user can then be assigned apartner, or may already have a partner.

At this point the partner can add various requirements for the user asshown at 1210. The requirements can include all those things the partnerbelieves will aid the user in recovery, judicial requirements, workrequirements, educational requirements, and the like. Themanager/partner can denote the frequency of each of the variousrequirements and indicate if the requirements are compulsory oroptional.

When the user opens the system at step 1215, all of the requirements forthe user for the given day can be displayed to the user. The user can beprompted to acknowledge such appointments at step 1220. Thisacknowledgement requires the user to begin the process of learning to beself-compliant. The acknowledgement further tells the manger that theuser has engaged with the system. If the user fails to acknowledgerequirements for a day or a few days, the manger can receive anotification as shown at step 1225 that the user may be sliding towardrecidivism or relapse.

As the user attends the required appointments for the day at step 1230,the user can verify their attendance using the system. The user can signin and sign out with the system to verify their attendance at step 1235.The disclosed system 400 can be used to verify attendance. As the userattends the appointments and verifies attendance the system can updatethe user metrics as shown at 1240 to indicate that the user has attendedthe appointments. The system can further update the manager or partnerat 1245, to indicate if the user has complied with the variousrequirements. As the user completes requirements and/or bonusappointments the system gives the user positive feedback at step 1250 toencourage the user. The method ends at 1255.

It should be understood that various steps in the method can be repeatedor rearranged and that the method continues each day, helping the userto learn to be accountable to themselves and others.

FIG. 13 illustrates a method 1300 for data collection and aggregation toidentify systemic success and failures associated with user complianceusing the systems disclosed herein. The method begins at 1305.

As various steps are completed in the method of FIG. 12 using the systemdisclosed herein, the system 400 can collect information related to themanager and aggregate that information with previously collectedinformation from the manager (or other hierarchical user) as illustratedat 1310. The system metrics can be analyzed at step 1315 by requirementtype, compliance rate, etc. to identify trends for the manager/partner.As the metrics are analyzed a user interface can be used to representthose metrics to a user at various levels as shown at 1320. The metricsallow system users to determine those managers that are effectivelymanaging users and to help identify those areas where the manger canimprove performance and offer better service to users. The method endsat 1325.

The disclosed systems and methods make real-time, broad-spectrum,holistic data available to each level of administration within anyorganization or agency, that enables those bodies to pinpoint who andwhat is working—and not working—and make changes accordingly. Becausethe results are available in real time, organizations have unprecedentedflexibility and fluidity in response to metrics.

Regardless what a particular agency does or the population it serves,the system can give them more accurate tools to address issues, whateverthey are. For example, in certain embodiments learning algorithms can beused to improve outcomes. The system can provide aggregation of broadcommunity metrics based on individual data. The individual patient isone data point where many such data points can be used to extrapolateoutcomes for a whole community.

The disclosed systems provide engagement of the client in aninteractive, real time relationship with their accountability partner.This contrasts sharply with prior approaches, which require forcedcompliance, and enforced accountability through passive monitoring ofclients, negative reinforcement/“violation” centered models.

By leveraging digital processes and tools to achieve learning outcomesfor improved long term benefits, the system brings togetherself-directed learning techniques with real-time personalaccountability, rather than negative reinforcement and apassive-coercive approach.

Because the system operates from a model of choice it offers markedimprovement in outcomes. The user takes ownership of his or her ownprocess and compliance. The geotagged and time stamped “selfie sign in”eliminates both the falsifiable/manipulative component, and the coercivedynamic, by offering clear verifiable data and tools that resistcorruption or manipulation. This method of generating engagedaccountability rather than passive coercion, shifts the dynamic ofstipulated responsibilities in treatment/corrections from anoverwhelming impasse to an interactive learning process. Also, thesystem can help improve outcomes through connection to local resourcestargeted at the specific problems the user identifies.

The systems and methods can be used to personalize outcomes to theindividual. It carries broad scope life metrics. Tracking acrossdifferent life areas means that administrators have access tointerdisciplinary data points. This data means that targeted, localizedchanges can be driven toward process outcomes and directionalimprovement.

It should be appreciated that the example embodiments have been directedto certain contexts. However, in other embodiment the interface candrive toward broad data aggregation rather than narrow, individual datatracking. The system can generate broad datasets based on differing usecase outcomes as well as demographic, local or staff-based breakdowns ofinformation.

A key to this system is remote accountability regardless of geographiclocation. Even for clients who leave the county or state can stillaccessible to accountability partners

The system further offers broader industrial benefits. Almost everyindustry has a need for compliance and accountability. By bringing thisnotion of multivariable, non-tracking, non-passive accountability intovarious contexts the system can be used in other forms from collegeathletes to offsite workers to people seeking to make diet/lifestylechanges to address chronic health conditions.

The system can be modular and is adaptable across industries andmodalities. The systems and methods can be applied across a wide rangeof applications. The integration of features provide a defined model,based on Al-potentiated data analytics. While the nine categories on theY-axis are changeable in themselves, they are also flexible andcombinable in terms of how that data may be analyzed.

For example, any employees who work remotely, away from directsupervision, can provide a potential use case for the system—not onlybecause it can provide the ability to “punch in” and “punch out” usingthe selfie sign in, but because they can sign in to different billingiterations, and the company can make use of the resource platform toprovide workers with the resources they need to complete their tasks.The system can verify in/out times at locations; integration betweenhome office and workers in the field in real time; integration ofresources and intersecting services through the platform. Maximizingefficiency while allowing workers autonomy both in their accountabilityand in integrated data acquisition.

In addition, the system provides the ability to accurately know wherepeople are and whether they are complying with requirements. It alsoallows real time changes to scheduling through the calendar and can beuseful for transport workers, regional sales forces, military,corrections, and enforcement agencies, academic programs, includingathletic programs, scholarship and support programs, and remedialsupport programs for students in development.

For example, the system can help students meet the various requirementsof their programs across disciplines—getting to class, tutoring,practice, medical appointments, etc.—again, real time accountability andverification allows intervention by coaches and support workers beforesetbacks grow into problems.

The sign in/sing out module (i.e. selfie sign-in) can be a three layeredtool that simultaneously identifies, locates, and time-stamps a photo.It accurately and instantly categorizes event, text adds identifiers,geolocated, and can use artificial intelligence algorithms (e.g. a NaiveBayes algorithm or other such algorithm) for facial recognition,providing time stamped verification that a user is where they aresupposed to be.

The system can also provide a blank resource platform—configurable withpertinent resources that the end user may want/need to pinpoint theirneeds. Client populated, segmentable geographically, vetted byusers/administrators to ensure accuracy. In embodiments, the resourceplatform can be populated by/for programs that work with substance abuseclients and their various needs. But a university or work forceapplication may make use of that resource platform in other embodiments.

In an exemplary embodiment the system can be used to help clientsstructure their recovery as they reintegrate into life, by helping tosupport integration of multimodal treatments, and providingaccountability and data for client compliance within and acrossagencies. The system also provides compliance and accountability asclients meet stipulated requirements. The system is flexible enough toaccommodate various protocols and requirements customized to each clienteven as it continues to aggregate data into meaningful and usefulstatistics to help address recidivism and program failure. The systemalso highlights successes within programs for clients and staff members;shows who and what works optimally to improve outcomes; again,verifiable, non-falsifiable data available in real-time to enforcementand accountability partners.

The disclosed systems are meant to help teach people skillsets theydon't have. Through practice and repetition the system can help clientsmake a choice to do something different. The system includes tools thathelp them learn skills around scheduling, accountability, andcompliance. The system thus includes a learning platform. For example,accountability partners can add mandatory schedules, but clientsthemselves can add appointments so they can continue to use thecalendar. In this way, the calendar gradually becomes their own.

In additional embodiments, targeted outcomes for clients can beprovided. In certain embodiments the system can use artificialintelligence to predictively help people over the course of extendedtimespans by identifying patterns in behavior at an early stage, makingearly intervention possible. The skills that clients need offer thechance to create long term success modeling, so as a person improves,the system can adapt to build accountability.

Continuous use of the systems and methods allows the demonstration ofimprovement over time. Setting baselines (first using the app blindly toset a control)—then adding a scoring system to indicate success orfailure—made or missed appointments, timeliness, accuracy, other metricscan be provided. Then targets can be set first by the accountabilitypartner, and then by the client, over time.

In certain embodiments the system can use common variables to predictand improve compliance. Artificial Intelligence can be used to performpattern seeking in behaviors. For example, does the client excel at workbut not at meeting attendance? The system can help accountabilitypartners analyze these patterns, or flags can be created based on suchdata analysis automatically.

When the system identifies what works or doesn't for individual clients,the system can target programming—and also make local, immediate,programming decisions that pinpoint personal and local challenges. Whyare a group of clients failing at a particular metric? Why are staffmembers more/less successful overall, or among themselves? Anotherquestion might be, do clients excel at meeting attendance but notcommunity service? Why? Another question might be, are there 12-stepmeetings accessible to the client? What compensatory services can we asa county provide, absent these? From these questions the system cancreate true success indicators for the client and extrapolate fromthose, better outcomes for managers by targeting areas of noncomplianceoverall.

Any manager will be able to see how they are connecting with theirclients by seeing how the clients are doing at compliance within certaincategories that might be indicative of larger problems. For example, oneclient group might be universally compliant at testing but not atparticipating in treatment. This allows programs to target programinterventions at particular challenges within their own modality, or toparticular manager's performance.

By aggregating even the basic data, the system can radically reduceadministrative time spent in paperwork and program audits. Real timeviews of staff performance allows unprecedented analysis of staff needsand strengths. The system can collect and integrate data from a numberof contexts—is the client showing up at work, as well as health care,counseling, judicial obligations, etc.?

Because the client, rather than their manager, is generating data, itsaves staff time and reduces administrative paperwork. The system canalso reduce or eliminate human error in collecting that data. The systemensures actual compliance, and produces real time data on the managerdashboard. The manager can be passive in the process. And like the phonemodule, the desktop features can work remotely—anywhere in the world.

This improves outcome for administration to see how well their staff isperforming without meetings, audits or additional work—real time data onmanager success. What starts on the client end of things as beneficialfor them extrapolates up into data metrics within and across theorganization.

The Manager's dashboard or portal likewise reinforces positivebehavior—encourages both clients and managers to go above and beyondcompliance to higher levels of action based on positive reinforcement.Going to more meetings, etc., generates gold stars for a client, butalso allows a manager to see success/risk factors in real time;managers' aggregated data allows staff members to be more influential inpersonal relationship with clients because accountability is theclient's responsibility, rather than staff member, so the staff memberis a partner rather than adversary.

For example, desktop, real time compliance data collected by the systemcan keep a corrections officer from having to be investigator and movesthem to client support role. Thus, the system provides accountabilityfor the managers. The system clearly illustrates who is succeeding withclients and in what pinpoint, real time ways a given manager—orprogram—is succeeding or not.

The system allows an administrator to review data from theirorganization and optimize it, testing solutions in real time. At theSuperadmin level, the system can compare regionally or organizationallywhat's working and what isn't working. The system can be used to mineout the nuggets of wisdom hidden in smaller programs and target programsor offices with particular challenges (there are no 12 step meetings ina certain town; how does that impact the success/failure of autonomousprogram in that town?).

Based on the foregoing, it can be appreciated that a number ofembodiments, preferred and alternative, are disclosed herein. Forexample in certain embodiments, an accountability system comprises auser device, the user device comprising a GPS receiver, a camera, and acomputer system, the computer system further comprising: at least oneprocessor, a graphical user interface, and a computer-usable mediumembodying computer program code, the computer-usable medium capable ofcommunicating with the at least one processor, the computer program codecomprising instructions executable by the at least one processor andconfigured for: displaying at least one required action, validating auser check-in and a user check-out associated with the at least onerequired action, and tracking user completion of the at least onerequired action; and a partner device, the partner device comprising asecond computer system, said second computer system further comprising:at least one processor, and a computer-usable medium embodying computerprogram code, the computer-usable medium capable of communicating withthe at least one processor, the computer program code comprisinginstructions executable by the at least one processor and configuredfor: adding the at least one required action for display on the userdevice, and monitoring the user completion of the at least one requiredaction.

In an embodiment, the system further comprises an accountability module,the accountability module being configured for generating a calendarserved to the client device with a calendar module according to the atleast one required action added with the partner device.

In an embodiment, the calendar module further displays the at least onerequired action on a calendar displayed on the user device.

In an embodiment, the system further comprises a user sign in module,the user sign in module configured for: identifying a current time,identifying a current location of the user device, and collecting animage of the user with the user device. In an embodiment, the systemfurther configured for verifying the image of the user against a storedimage, verifying the current location of the user device is within ageofenced location associated with a current required action, andverifying the current time matches a time associated with a currentrequired action.

In an embodiment, the system further comprises a resource list providedon the user device with the graphical user interface.

In an embodiment, the system further comprises an alerts module, thealerts module configured for providing a notification of at least one ofan upcoming required action and a missed required action.

In an embodiment, the at least one required action further comprises atype comprising one of: a 12 step program, a judicial/probationrequirement, a testing requirement, an individual counselingrequirement, a group counseling requirement, a community servicerequirement, a medical requirement, a work requirement, and an otherrequirement. The at least one required action displayed on the userdevice can be color coded according to the type.

In an embodiment an accountability system comprises a user device, theuser device comprising a computer system, said computer system furthercomprising at least one processor, a GPS receiver, a camera, a graphicaluser interface, and a computer-usable medium embodying computer programcode, the computer-usable medium capable of communicating with the atleast one processor, the computer program code comprising instructionsexecutable by the at least one processor and configured for: displayingat least one required action, validating a user check-in and a usercheck-out associated with the at least one required action using a usersign in module, the user sign in module configured for: identifying acurrent time, identifying a current location of the user device, andcollecting an image of the user with the user device, and tracking usercompletion of the at least one required action; a partner device, thepartner device comprising a second computer system, the second computersystem further comprising: at least one processor; and a computer-usablemedium embodying computer program code, the computer-usable mediumcapable of communicating with the at least one processor, the computerprogram code comprising instructions executable by the at least oneprocessor and configured for: adding the at least one required actionfor display on the user device and monitoring the user completion of theat least one required action; and an accountability module, theaccountability module being configured for generating a calendar servedto the client device with a calendar module.

In an embodiment, the accountability module updates a calendar module onthe user device, wherein the calendar module displays the at least onerequired action on a calendar displayed on the user device.

In an embodiment, the user sign in module is further configured forverifying the image of the user against a stored image, verifying thecurrent location of the user device is within a geofenced locationassociated with a current required action, and verifying the currenttime matches a time associated with a current required action.

In an embodiment, a method for tracking accountability comprises addingat least one required action for display on a user device, with apartner device, displaying at least one required action on a userdevice, validating a user check-in and a user check-out associated withthe at least one required action with the user device, tracking usercompletion of the at least one required action with the user device, andmonitoring the user completion of the at least one required action withthe partner device.

In an embodiment, the method further comprises displaying a calendarwith the user device indicating the at least one required action,prompting user acknowledgement of the at least one required actionscheduled for a present day.

In an embodiment the method further comprises identifying a current timewith a user sign in module, verifying the current time matches a timeassociated with the at least one required action, identifying a currentlocation of the user device with a GPS receiver associated with the userdevice, verifying the current location of the user device is within ageofenced location associated with the at least one required action,collecting an image of the user with the user device, and verifying theimage of the user against a stored image of the user.

In an embodiment of the method the at least one required action furthercomprises a type comprising one of a 12 step program, ajudicial/probation requirement, a testing requirement, an individualcounseling requirement, a group counseling requirement, a communityservice requirement, a medical requirement, a work requirement, and another requirement.

It should be appreciated that variations of the above-disclosed andother features and functions, or alternatives thereof, may be desirablycombined into many other different systems or applications. It should beunderstood that various presently unforeseen or unanticipatedalternatives, modifications, variations or improvements therein may besubsequently made by those skilled in the art which are also intended tobe encompassed by the following claims.

What is claimed is:
 1. An accountability system comprising: a userdevice, the user device comprising a GPS receiver, a camera, and acomputer system, the computer system further comprising: at least oneprocessor; a graphical user interface; and a computer-usable mediumembodying computer program code, the computer-usable medium capable ofcommunicating with the at least one processor, the computer program codecomprising instructions executable by the at least one processor andconfigured for: displaying at least one required action; validating auser check-in and a user check-out associated with the at least onerequired action; and tracking user completion of the at least onerequired action; and a partner device, the partner device comprising asecond computer system, said second computer system further comprising:at least one processor; and a computer-usable medium embodying computerprogram code, the computer-usable medium capable of communicating withthe at least one processor, the computer program code comprisinginstructions executable by the at least one processor and configuredfor: adding the at least one required action for display on the userdevice; and monitoring the user completion of the at least one requiredaction.
 2. The accountability system of claim 1 further comprising: anaccountability module, the accountability module being configured forgenerating a calendar served to the user device with a calendar moduleaccording to the at least one required action added with the partnerdevice.
 3. The accountability system of claim 2 wherein the calendarmodule further displays the at least one required action on a calendardisplayed on the user device.
 4. The accountability system of claim 2further comprising: a user sign in module, the user sign in moduleconfigured for: identifying a current time; identifying a currentlocation of the user device; and collecting an image of the user withthe user device.
 5. The accountability system of claim 4 furthercomprising: verifying the image of a user against a stored image.
 6. Theaccountability system of claim 4 further comprising: verifying thecurrent location of the user device is within a geofenced locationassociated with a current required action.
 7. The accountability systemof claim 4 further comprising: verifying the current time matches a timeassociated with a current required action.
 8. The accountability systemof claim 1 further comprising: a resource list provided on the userdevice with the graphical user interface.
 9. The accountability systemof claim 1 further comprising: an alerts module, the alerts moduleconfigured for providing a notification of at least one of: an upcomingrequired action; and a missed required action.
 10. The accountabilitysystem of claim 1 wherein the at least one required action furthercomprises a type comprising one of: a 12 step program; ajudicial/probation requirement; a testing requirement; an individualcounseling requirement; a group counseling requirement; a communityservice requirement; a medical requirement; a work requirement; and another requirement.
 11. The accountability system of claim 10 wherein theat least one required action displayed on the user device can be colorcoded according to the type.
 12. An accountability system comprising: auser device, the user device comprising a computer system, said computersystem further comprising: at least one processor; a GPS receiver; acamera; a graphical user interface; and a computer-usable mediumembodying computer program code, the computer-usable medium capable ofcommunicating with the at least one processor, the computer program codecomprising instructions executable by the at least one processor andconfigured for: displaying at least one required action; validating auser check-in and a user check-out associated with the at least onerequired action using a user sign in module, the user sign in moduleconfigured for: identifying a current time; identifying a currentlocation of the user device; and collecting an image of the user withthe user device; and tracking user completion of the at least onerequired action; a partner device, the partner device comprising asecond computer system, the second computer system further comprising:at least one processor; and a computer-usable medium embodying computerprogram code, the computer-usable medium capable of communicating withthe at least one processor, the computer program code comprisinginstructions executable by the at least one processor and configuredfor: adding the at least one required action for display on the userdevice; and monitoring the user completion of the at least one requiredaction; and an accountability module, the accountability module beingconfigured for generating a calendar served to the user device with acalendar module.
 13. The accountability system of claim 12 wherein theaccountability module updates a calendar module on the user device,wherein the calendar module displays the at least one required action ona calendar displayed on the user device.
 14. The accountability systemof claim 13 wherein the user sign in module is further configured for:verifying the image of the user against a stored image.
 15. Theaccountability system of claim 13 wherein the user sign in module isfurther configured for: verifying the current location of the userdevice is within a geofenced location associated with a current requiredaction.
 16. The accountability system of claim 13 wherein the user signin module is further configured for: verifying the current time matchesa time associated with a current required action.
 17. A method fortracking accountability, the method comprising: adding at least onerequired action for display on a user device, with a partner device;displaying at least one required action on a user device; validating auser check-in and a user check-out associated with the at least onerequired action with the user device; tracking user completion of the atleast one required action with the user device; and monitoring the usercompletion of the at least one required action with the partner device.18. The method for tracking accountability of claim 17 furthercomprising: displaying a calendar with the user device indicating the atleast one required action; and prompting user acknowledgement of the atleast one required action scheduled for a present day.
 19. The methodfor tracking accountability of claim 17 further comprising: identifyinga current time with a user sign in module; verifying the current timematches a time associated with the at least one required action;identifying a current location of the user device with a GPS receiverassociated with the user device; verifying the current location of theuser device is within a geofenced location associated with the at leastone required action; collecting an image of the user with the userdevice; and verifying the image of the user against a stored image ofthe user.
 20. The method for tracking accountability of claim 17 whereinthe at least one required action further comprises a type comprising oneof: a 12 step program; a judicial/probation requirement; a testingrequirement; an individual counseling requirement; a group counselingrequirement; a community service requirement; a medical requirement; awork requirement; and an other requirement.